Supersedes #1667, as there were issues with DCO sign-off

It works e2e with openid4vc issuance, and verification with SD-JWT-VC, BUTT there's still some todos, but If possible I'd like to do it in follow up PRs as this one is already huge.

Some of the todos:

• add events so you can hook into the state changes of offers/requests
• Update some FIXMEs once PRs have been merged into PEX/OID4VC/SD-JWT libraries (it's currently all working, but sometimes a bit hacky)
• add support for request_uri as the QR for presentation requests can get quite large at the moment
• Add improvements to the API so it's known as a holder which field will be selectively disclosed (you now just get the record)
• Issue that awesome-qr MUST be installed on react native
• support jwk thumbprint in Sphereon siop/oid4vp libs (currently only dids are supported for proving, opened Best way to support JWK thumbprint as subject_syntax_type? Sphereon-Opensource/OID4VC#154, but this requires some substantial work)
• Allow presenting multiple SD-JWT vcs in a single request. My first option was to go for creating multiple VPs for a single presentation definitoin and submission, but this is not supported by PEX/OID4VP libraries from Sphereon (See Sending multiple VPs with a single presentation definition Sphereon-Opensource/SIOP-OID4VP#62). It does support multiple Presentation definitions, so maybe that's the way to go (although I'd like using one PD more)
• Replace the in-memory session with something persistent

Here's a list of PRs that if released will allow for some cleanup on our side (but we can do that after this PR is merged):

• feat: calculate and verify sd-hash berendsliedrecht/sd-jwt-ts#35
• fix: base64url react native berendsliedrecht/sd-jwt-ts#33
• feat: allow passing issuer and kb jwk berendsliedrecht/sd-jwt-ts#34
• fix: do not use path nested for sd-jwt Sphereon-Opensource/PEX#140
• fix: import response type Sphereon-Opensource/SIOP-OID4VP#71
• fix: check presentation callback result Sphereon-Opensource/SIOP-OID4VP#70